Schedule overrides api timezone issues

#1

We are using Time Zone: Europe/Copenhagen in our schedule.
When creating an override, from the api, it somehow translates this to a different time zone.
Is there a way to add a reference so the override is created in the correct time zone?
(see image below)

When using the gui, this is not a problem, this only occurs when using the api.

I have used this api reference: https://api-reference.pagerduty.com/#!/Schedules/post_schedules_id_overrides

image

#2

Hey Camilla,

The timezone is showing the UTC format of the schedule override in the Response Body. This is expected behaviour but the Schedule Override should still be in the desired outcome of your schedule.

When I submit:

 "override": {
    "start": "2020-02-01T00:00:00-04:00",
    "end": "2020-02-02T00:00:00-04:00",
    "user": {
      "id": "USER_ID",
      "type": "user_reference"
    }
  }

The response body shows the respective time to be "2020-02-01T04:00:00Z and “2020-02-02T04:00:00Z” which align with how the time should appear in UTC time. The web UI correctly displays the schedule override to be from 2020-02-01T00:00:00-04:00 to 2020-02-02T00:00:00-04:00.

Cheers,

#3

Hi

As I understand your answer, it should work - but it doesn’t display the correct within pagerduty.
Try to change your schedule to timezone Europe/Copenhagen and you should be able to replicate the issue.

Request: I expect the on-call schedule to start from 07:00 and end at 12:00 Europe/Copenhagen.

{
“override”: {
“start”: “2020-04-15T07:00:00-04:00”,
“end”: “2020-04-15T12:00:00-04:00”,
“user”: {
“id”: “user_id”,
“type”: “user_reference”
}
}
}

Pagerduty:
image

#4

Hi Camilla,

Please correct me if I’m wrong but I believe Copenhagen time is Central European Standard Time (CET) which is 1 hour ahead of UTC/GMT.

Per your screenshots, you’re sending the time in UTC-04:00 vs. UTC+01:00 which would result in using Eastern Daylight Time or Atlantic Time Zone.

If you submit the request as the following, it should capture your desired time zone:

"override": {
    "start": "2020-02-01T00:00:00+01:00",
    "end": "2020-02-02T00:00:00+01:00",
    "user": {
      "id": "USER_ID",
      "type": "user_reference"
    }
  }

The +/-HH:MM aspect would be what defines the timezone.

#5

Ahh, I just took the sample from the api. :sweat_smile:
That, was exactly what I was looking for - thanks a bunch!